However, there is such a description in Snowflake:

If updateFlag is set to TRUE, then the existing input key is updated to the input value

But in Databend, do we support dynamically setting config in the query? Alternatively, we can set the config when querying with the bendsql?

However, there is such a description in Snowflake:

If updateFlag is set to TRUE, then the existing input key is updated to the input value

But in Databend, do we support dynamically setting config in the query? Alternatively, we can set the config when querying with the bendsql?

We can register a new function with four arguments for map_insert, for example st_geometryfromwkb can support two and three args.

But, I have discovered a problem now:

CREATE TABLE map_insert_test(col_str Map(String, String Null) Not Null, col_int Map(String, Int Null) Null);

SELECT map_insert(col_int, 'a', 100)
FROM map_insert_test;

For the NULL map, it is currently stuck and unable to run. However, I tried to modify the domain calculation, but it had no effect. I have no idea here 😣

But, I have discovered a problem now:

CREATE TABLE map_insert_test(col_str Map(String, String Null) Not Null, col_int Map(String, Int Null) Null);

SELECT map_insert(col_int, 'a', 100)
FROM map_insert_test;

For the NULL map, it is currently stuck and unable to run. However, I tried to modify the domain calculation, but it had no effect. I have no idea here 😣

Both val_domain and insert_value_domain may be nullable, and we need to deal with various cases, such as

match (val_domain, insert_value_domain) {
    (Domain::Nullable(NullableDomain {..}), Domain::Nullable(NullableDomain {..})) => ...,
    (Domain::Nullable(NullableDomain {..}), _) => ...,
    (_, Domain::Nullable(NullableDomain {..})) => ...,
    (_, _) => ...,
}

Thanks for @hanxuanliang PR. And look forward to keeping an eye on databend in the future